Create mock.nf in project folder instead of meta folder
#198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This will fix an issue I've have with relative imports of modules, for example having something like this in a workflow
Will not work in the meta dir when projectDir isn't resolved to the top level |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the creation of the
mock.nffile in the project folder (instead of themetafolder) to preserve Nextflow'sprojectDir. The mock file has a unique name (.nf-test-${test-hash}.nf) and after execution, the file is moved to themetafolder for debugging purposes. Consequently, there's no longer a need to stage files to the meta directory.This PR addresses the following issues:
assetsbinandlibfolders broken #193).projectDirreferences become invalid under nf-test #99 (comment)).Additionally, this change could resolve the issue: